Closed
Conversation
Member
keegancsmith
left a comment
There was a problem hiding this comment.
FYI you probably want to update the workflow files as well. This does work, but then each github action will download the relevant go toolchain since this go directive is a higher version.
Also while we are here, use the latest: 1.25.4
keegancsmith
approved these changes
Nov 11, 2025
Member
|
FYI #1198 will make it so you only need to update .tool-versions to get all CI workflows using that version. |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addressing
src-cliconcern in https://sourcegraph.slack.com/archives/C05DWT4ANHH/p1762881342663879 by upgradeing go to minimum version that addresses vulns1.24.9Found the following vulns initially with
govulncheck ./...Details
Test plan
built locally, reran
govulncheck ./...